@opentelemetry/scope-base

OpenTelemetry Base Scope Manager

This package provides the ScopeManager interface (which is used by concrete implementations) and a no-op implementation (which is used internally when no scope propagation is defined). It's intended for use both on the server and in the browser.

What is a Scope Manager ?

To understand why they exists, we'll need to understand how Javascript works: when you make native function call (networks, setInterval etc) you generally call C++ code that will later callback your own code.

A common issue when tracing a request in javascript is to link the function that have made the native call to the callback that the native code called when the response is there. Imagine you want to track for which user you made the request, you need some sort of "context/scope aware storage".

ScopeManager's aim to offer exactly that, it's API offer to store an object in the current scope (with()) and if needed, bind() to a specific function call to find it back when the callback fire, which can later get retrieved using active().

This package only include the interface and a Noop implementation, for more information please see the async-hooks based ScopeManager for NodeJS.

Note: You will sometimes read about context management, which is sometimes also used for talking about scope management. However in OpenTelemetry, context was already heavily used as a concept in the Trace API so we named this package with scope to avoid confusion.

Useful links

• For more information on OpenTelemetry, visit: https://opentelemetry.io/
• For more about OpenTelemetry JavaScript: https://github.com/open-telemetry/opentelemetry-js
• For help or feedback on this project, join us on gitter

License

Apache 2.0 - See LICENSE for more information.

Changelog

0.3.3

Released 2020-01-22

:rocket: (Enhancement)

• opentelemetry-core, opentelemetry-exporter-collector, opentelemetry-exporter-zipkin, opentelemetry-node, opentelemetry-plugin-dns, opentelemetry-plugin-document-load, opentelemetry-plugin-grpc, opentelemetry-plugin-http, opentelemetry-plugin-https, opentelemetry-plugin-ioredis, opentelemetry-plugin-mongodb, opentelemetry-plugin-mysql, opentelemetry-plugin-postgres, opentelemetry-plugin-redis, opentelemetry-plugin-xml-http-request, opentelemetry-shim-opentracing, opentelemetry-tracing, opentelemetry-types, opentelemetry-web
  • #582 Named Tracers / Tracer Registry
• opentelemetry-node, opentelemetry-plugin-postgres
  • #662 feat: add pg-pool to default list of instrumented plugins
  • #708 Simplify and speed up trace context parsing
• opentelemetry-metrics
  • #700 implement named meter

:sparkles: (Feature)

• opentelemetry-propagator-jaeger
  • #701 add jaeger http trace format
• opentelemetry-exporter-stackdriver-trace
  • #648 Stackdriver Trace exporter

:books: (Refine Doc)

• #673 chore(getting-started): Added a TypeScript version for Getting Started Guide

:bug: (Bug Fix)

• opentelemetry-plugin-ioredis
  • #714 fix: return module exports from ioredis